Systems and methods for redundant array data alignment

ABSTRACT

A data alignment (DA) computing device is communicatively coupled to a first and a second data storage device. The first data storage device stores an array of partitions including a first subset and a second subset of partitions, and metadata associated with the array that includes a reference pointer for each partition. The DA computing device updates the metadata to remove the reference pointers for the second subset of partitions and thereby remove the second subset from the array, stores a partition table defining the first subset within the first data storage device and the second subset within the second data storage device, stores the metadata associated with the array within the second data storage device, updates the second data storage device to include the second subset of partitions, and updates the metadata stored by the data storage devices to link the second subset of partitions to the array.

BACKGROUND

The field of the present disclosure relates generally to data storageconfigurations, and more specifically, data alignment of partitionedstorage devices during an operating system conversion.

Servers and other data storage devices are used to store and communicatedata for various applications. For example, servers may be used to storedata associated with a payment network that facilitates transactionsusing payment cards (e.g., credit or debit cards) and payment accounts.The servers typically include a plurality of data storage devices (e.g.,hard disk drives and solid state drives) to provide data redundancyand/or increased data storage. An operating system is installed on eachserver to enable the server to perform standard functions, such ascommunicate with other devices, store data, and display a graphical userinterface (GUI). The operating system includes a set of protocols foreach function such that data is received, processed, and transmittedaccording to a specific format supported by the operating system. Forexample, an operating system may include one or more file systemarchitectures for connected storage devices to store data, such as fileallocation table (FAT), fourth extended filesystem (ext4), and newtechnology file system (NTFS).

In some cases, the servers may be scheduled to switch or convertoperating systems (i.e., due to lack of support, alternative operatingsystems, etc.). However, converting between operating systems may causeissues with data stored in a file system architecture that is notsupported by the new operating system. Accordingly, the server mayrequire on-site technical overview, additional data storage devices,and/or one or more reboots to install the new operating system. The downtime caused by the installation and conversion process may be long andinconvenient for users attempting to access the server and the datastored by the server, particularly for data critical to a particularprocess or service performed by the server.

BRIEF DESCRIPTION

In one aspect, a data alignment (DA) computing device includes aprocessor communicatively coupled to a first data storage device and asecond data storage device, and a memory in communication with theprocessor. The first data storage device stores an array of partitionsand metadata associated with the array of partitions. The array ofpartitions includes a first subset of partitions and a second subset ofpartitions mirroring the first subset of partitions and the metadataincludes a reference pointer for each partition of the array ofpartitions. The memory stores instructions that, when executed by theprocessor, cause the processor to update the metadata to remove thereference pointers for the second subset of partitions and therebyremove the second subset of partitions from the array of partitions,store, within the first and second data storage devices, a partitiontable that defines the first subset of partitions within the first datastorage device and the second subset of partitions within the seconddata storage device, store the metadata associated with the array ofpartitions within the second data storage device, update the second datastorage device to include the second subset of partitions, and updatethe metadata stored by the first data storage device and the second datastorage device to link the second subset of partitions to the array ofpartitions.

In another aspect, a method for aligning data in array of partitionsincluding a first subset of partitions and a second subset of partitionsis provided. A first data storage device stores the array of partitionsand metadata associated with the array of partitions. The method is atleast partially performed by a DA computing device. The method includesupdating the metadata to remove reference pointers for the second subsetof partitions and thereby remove the second subset of partitions fromthe array of partitions, storing, within the first data storage deviceand a second data storage device, a partition table that defines thefirst subset of partitions within the first data storage device and thesecond subset of partitions within the second data storage device,storing the metadata associated with the array of partitions within thesecond data storage device, updating the second data storage device toinclude the second subset of partitions, and updating the metadatastored by the first data storage device and the second data storagedevice to link the second subset of partitions to the array ofpartitions.

In yet another aspect, at least one non-transitory computer-readablestorage media having computer-executable instructions embodied thereonis provided. When executed by at least one processor, thecomputer-executable instructions cause the processor to update metadataassociated with an array of partitions including a first subset ofpartitions and a second subset of partitions to remove referencepointers for the second subset of partitions and thereby remove thesecond subset of partitions from the array of partitions. The metadataand the array of partitions are stored on a first data storage device.The instructions further cause the processor to store, within the firstand second data storage devices, a partition table that defines thefirst subset of partitions within the first data storage device and thesecond subset of partitions within the second data storage device, storethe metadata associated with the array of partitions within the seconddata storage device, update the second data storage device to includethe second subset of partitions, and update the metadata stored by thefirst data storage device and the second data storage device to link thesecond subset of partitions to the array of partitions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-7 show example embodiments of the methods and systems describedherein.

FIG. 1 is a block diagram illustrating an example data alignment (DA)system for aligning data during an operating system conversion inaccordance with one embodiment of the disclosure.

FIG. 2 is a block diagram of an example DA system including a DAcomputing device in communication with a host computing device.

FIG. 3 is an example data schematic of the system shown in FIG. 1.

FIG. 4 is an expanded block diagram of an example embodiment of a remotedevice for use in the system shown in FIG. 1.

FIG. 5 illustrates an example configuration of a host system for use inthe system shown in FIG. 1.

FIG. 6 is a flowchart of an example process for aligning data during anoperating system conversion using the system shown in FIG. 1.

FIG. 7 is a diagram of components of one or more example computingdevices that may be used in embodiments of the described systems andmethods.

DETAILED DESCRIPTION

Systems and method according to this disclosure are directed to datastorage configurations, and more specifically, data alignment ofpartitioned storage devices during operating system conversion.

A data alignment (DA) system is described herein for aligning datastorage partitions across multiple physical data storage devices,particularly during a conversion between operating systems (OSes). Inthe example embodiment, the DA system includes a first data storagedevice and a second data storage device. The first and second datastorage devices may be hard disk drives (HDDs), solid state drives(SSDs), and/or any other suitable type of data storage. Each datastorage device includes a plurality of partitions. In at least someembodiments, the first and second data storage devices are configured ina multiple disk (MD) array for data redundancy, increased storage,and/or improved performance. For example, the first and second datastorage devices may be in a redundant array of independent disks (RAID)configuration, such as RAID 1 or RAID 5. In the RAID 1 configuration,data stored on the first data storage device is mirrored or copied tothe second data storage device. As used herein, a “mirror” refers to aplurality of partitions within a redundant array that store matchingcopies of data. Redundant arrays, such as RAID 1, are used to preventdata loss in the event of a storage device failure. That is, when apartition or storage device within the redundant array fails, a copy ofthe data stored by the failed partition is accessible via a respectivemirror within the array.

In the example embodiment, the first and second data storage devicesstore metadata associated with the redundant array. The metadataincludes a reference pointer for each partition within the redundantarray. In some embodiments, the reference pointer identifies a blockdevice file associated with the partition. The block device file is aninterface to enable software to interact with a device driver of thedata storage devices to read and write data on the partitions. In oneexample, the reference pointer is associated with a block deviceidentifier that references a respective block device file. In at leastsome embodiments, the metadata is part of a superblock stored by boththe first and second data storage devices.

In the example embodiment, the first and second data storage devices arein communication with one or more processors and a memory deviceconfigured to store instructions for the processors. The first andsecond data storage devices store instructions and data associated withan OS that, when executed by the processors, cause the processors tooperate as a computing device, such as a server. The OS includes a setof specific formats and protocols for various functions of the computingdevice, including, but not limited to, file system architectures,network protocols, kernel architecture, and the like. The first andsecond data storage devices are formatted in accordance with one or morefile system architectures supported by the installed OS.

In at least some embodiments, the installed OS (“first OS”) may bereplaced by a new OS (“second OS”). For example, if the installed OS isdepreciated due to lack of support, a new OS may be installed on thecomputing device. To convert to the computing device to a second OS, animage file associated with the second OS is executed by the processorsto install the second OS on at least one of the first and second datastorage devices. In the example embodiment, the second OS is installedon the first data storage device while the second data storage devicehas the first OS installed. More specifically, a partition (referred toherein as an “OS partition”) is generated on each data storage device toinstall the respective OS such that a user can test the second OS whileretaining the ability to return to the first OS. The OS partition isformatted in a particular file system architecture supported by therespective OS (but may not be supported by the other OS). Additionalpartitions may be installed on the first and second data storage devicesto store data. In certain embodiments, the additional partitions may beformatted in a file system architecture that is supported by both thefirst and second OS.

To prevent the redundant array from synchronizing across the first andsecond data storage device (which would overwrite one of the OSpartitions), a kickstart configuration file is executed with the imagefile to configure the array on a single data storage device (i.e., thefirst data storage device). That is, the kickstart configuration fileconfigures the array to only include partitions of the first datastorage device and treats the other half of the mirror as a faileddevice. By treating part of the mirror as a failed device, the second OSdoes not overwrite the data on the second data storage device tocomplete the mirrors of the array. Rather, the array continues tooperate with at least partition in each mirror. Accordingly, both thefirst and second OSes are stored and can be selectively initiated by thecomputing device. After a determination is made to fully convert to thesecond OS, the first OS is removed and the redundant array is updated tofully utilize the first and second data storage devices.

In the example embodiment, the DA system includes a DA computing device.In some embodiments, the DA computing device includes the processors incommunication with the first and second data storage devices and thememory device. In other embodiments, the DA computing device iscommunicatively coupled to the processors in communication with thefirst and second data storage devices. In such embodiments, theprocessors and the memory device are part of a host computing deviceincluding the first and second data storage devices.

The DA computing device is configured to align the first and second datastorage devices by performing a data alignment process to enable thefirst and second data storage devices to operate as an array with thesecond OS. That is, to operate the data storage devices in an array, thepartitions within the first and second data storage devices must includematching sizes and matching file systems to be added to a respectivemirror. In at least some known systems, aligning two data storagedevices may require additional data storage devices and/or one or morereboots of the computing device to initialize the array, which mayinterrupt services provided by the computing device. In the exampleembodiment, the DA computing device uses the “failed” devices asconfigured by the kickstart configuration file and the “hot-swap”capability of the redundant array to align the first and second datastorage devices without using additional data storage devices orrebooting the computing device.

In the example embodiment, the DA computing device is configured todetermine whether or not the first and/or second data storage devicesare undergoing synchronization or a mirror recovery process beforealigning the data storage devices. More specifically, the DA computingdevice analyzes the metadata to detect any ongoing synchronization orrecovery process. The metadata includes a state file or state data thatindicates the current state of each mirror in the array. Afterdetermining no synchronization or recovery process is occurring, the DAcomputing device begins the data alignment process.

The DA computing device is further configured to set a data transferspeed for the mirrors within the array to facilitate performing the dataalignment process in the background without interrupting the processesor services using the data stored in the first and second data storagedevices. In some embodiments, the DA computing device generates andtransmits instructions to the block device files associated with thearray mirrors to set data transfer speed boundaries.

The DA computing device scans the metadata to identify and remove anydata associated with previous arrays. When the DA computing devicedetects data associated with a previous array, the DA computing deviceoverwrites or removes the data to prevent the data from affecting thedata alignment process. The DA computing device may scan the metadata toremove data associated with any previous arrays several times throughoutthe data alignment process.

The DA computing device updates the metadata stored at least by thefirst data storage device to remove the reference pointers to thepartitions identified as failed devices by the kickstart configurationfile. As used herein, the “first subset of partitions” refer topartitions stored by the first data storage device that are notidentified as failed devices, and the “second subset of partitions”refer to the partitions identified as failed devices. In at least someembodiments, the DA computing device removes the reference pointersassociated with the second subset of partitions from the metadata.

In the example embodiment, the DA computing device generates a partitiontable for the first and second data storage devices. In someembodiments, the DA computing device retrieves the partition table froma remote computing device. The partition table includes data definingpredefined partitions to be generated on the respective data storagedevice by the data alignment process. The partition table also includesadditional information for each partition, such as data capacity,current used data size, and a block device identifier for eachpartition. The block device identifier is data or a pointer indicating ablock device file associated with the partition. In the exampleembodiment, the partition table includes data entries that match thefirst subset of partitions and the second subset of partitions. The DAcomputing device stores the partition table on the second data storagedevice to overwrite an existing partition table stored by the seconddata storage device. Overwriting the existing partition table removesthe previous partitions from the second data storage device, includingthe OS partition storing the initial OS. In the example embodiment, theDA computing device stores the metadata associated with the array ofpartitions on the second data storage device such that matching metadatais stored by the first and second data storage devices. Storing matchingmetadata enables the array to operate correctly even in the event of thefirst or second data storage device malfunctioning. Accordingly, whenupdating or otherwise editing the metadata, the metadata is updatedwithin both the first and the second data storage devices.

In the example embodiment, the DA computing device is configured toupdate the second data storage device to include the second subset ofpartitions. More specifically, the DA computing device removes at leastone block device identifier associated with previous partitions from thesecond data storage device. The DA computing device then scans thestored partition table for the second subset of partitions and generatesnew block device identifiers for the second subset of partitions on thesecond data storage device based on the partition table. By removing theprevious block device identifiers and generating new device identifiersfor a subset of partitions that was previously associated with faileddevices, the DA computing device has moved a portion of the array ofpartitions from a single data storage device to two data storage deviceswithout requiring the computing device to be rebooted. That is, the DAcomputing device uses the hot-swap capability of the redundant array tomove the second subset of partitions to the second data storage devicewithout interrupting services or processes using the data stored by thefirst and second data storage devices.

In the example embodiment, the DA computing device is configured to linkthe second subset of partitions to the array of partitions by updatingthe metadata stored the first and second data storage devices to includethe reference pointers associated with the second subset of partitions.The reference pointers are configured to reference or identify the newblock device identifiers of the second data storage device. The secondsubset of partitions is synchronized with the first subset of partitionsto mirror the data stored by the first subset of partitions.

To align the data storage devices, the first data storage device is alsoconfigured to match the second data storage device because at least someredundant arrays (i.e., RAID 1) require each mirror in the redundantarray to include at least two matching partitions. The DA computingdevice performs a process for the first data storage device that issimilar to the process for the second data storage device. Inparticular, in the example embodiment, the DA computing device: (i)removes the reference pointers associated with the first subset ofpartitions from the metadata, (ii) stores the partition table from thesecond data storage device, (iii) removes at least one block deviceidentifier associated with the first subset of partitions from the firstdata storage device, (iv) scans the stored partition table to generatenew block device identifiers for the first subset of partitions on thefirst data storage device, and (v) updates the metadata to includereference pointers for the first subset of partitions, thereby linkingthe first subset of partitions back to the array of partitions. Duringconfiguration of the first data storage device, the second data storagedevice is accessible for retrieving and storing data, thereby preventinginterruption of any services or processes performed using the datastored the first and second data storage devices. After the metadata hasbeen updated to include the reference pointers for the first subset ofpartitions, the data of the first and second data storage devices hasbeen aligned and the array of partitions is configured to use both datastorage devices.

In the example embodiment, the DA computing device expands at least onemirror of the array to include any unused space on the first and seconddata storage devices. Each mirror includes at least one partition fromeach data storage device, and therefore expanding one mirror will expandthe respective partitions on each data storage device. The DA computingdevice then saves the metadata to an array configuration file associatedwith the redundant array such that the array will remain after anyreboots. In at least some embodiments, the DA computing device installsa boot loader, such as Grand Unified Bootloader (GRUB), on both thefirst and the second data storage devices such that the new OS isbootable from either data storage device. The boot loader is configuredto determine which devices, and in what order, to access to initiate anOS.

In some embodiments in which the DA computing device is directly incommunication with the data storage devices, the DA computing device mayreceive a script or set of instructions from a remote computing devicethat cause the DA computing device to perform the data alignment processdescribed above. In other embodiments, the DA computing device is incommunication with a host computing device including the first andsecond data storage devices. In such embodiments, the DA computingdevice is configured to generate scripts that cause the host computingdevice to perform the data alignment process. Alternatively, the scriptmay be generated and processed locally (i.e., not received from anothercomputing device). Using scripts enables the data alignment process tobe at least partially automated to reduce the professional overviewneeded to complete the process.

To generate the scripts, the remote computing device or the DA computingdevice is configured to collect environment variables associated withthe data storage devices, such as, but not limited to, a log file data,a host name, and a disk size associated with the first and second datastorage devices. The log file data identifies a location and format of alog file that records information about the script as it is processed bythe receiving computing device. The host name identifies the computingdevice designated to run the script. These environment variables arecollected and inserted into the script to customize the script for aparticular recipient computing device.

The methods and systems described herein may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware or any combination or subset thereof,wherein the technical effects may be achieved by performing one of thefollowing steps: (i) updating metadata associated with an array ofpartitions including a first and second subset of partitions to removethe second subset of partitions by identifying the second subset ofpartitions as failed partitions; (ii) storing a partition table at thefirst and second data storage devices that identifies the first andsecond subset of partitions; (iii) updating the second data storagedevice to include the second subset of partitions by removing at leastone block device identifier associated with previous partitions from thesecond data storage device and scanning the stored partition table forthe second subset of partitions to generate new block device identifiersfor the second subset of partitions; (iv) linking the second subset ofpartitions to the array of partitions by updating the metadata toinclude the reference pointers of the second subset of partitions thatare associated with the new block device identifiers for the secondsubset of partitions; (v) after linking the second subset of partitionsto the array of partitions, removing the reference pointers removing thereference pointers associated with the first subset of partitions fromthe metadata; (vi) removing at least one block device identifierassociated with the array of partitions from the first data storagedevice; (vii) scanning the stored partition table for the first subsetof partitions to generate new block device identifiers for the firstsubset of partitions on the first data storage device; (viii) updatingthe metadata to include the reference pointers for the first subset ofpartitions; (ix) expanding at least one partition of the first andsecond subset of partitions to include unused data storage space of thefirst and second data storage devise; and (x) installing a boot loaderon the first and second data storage devices to enable an operatingsystem stored on the first and second data storage devices to initializefrom the first data storage device or the second data storage device.

The systems and methods described herein are configured to facilitate(a) reducing bandwidth and processing interference with services andprocesses using data stored on data storage devices converting betweenOSes; (b) reducing professional overview by automating the dataalignment process using scripts; (c) reducing time needed to align anarray on two data storage devices by performing the data alignmentprocess in the background; and (d) improved data security by providingthe option to return to the initial OS while testing the new OS in aredundant array.

Described herein are computer systems such as a host computing deviceand a DA computing device. As described herein, all such computersystems include a processor and a memory.

Further, any processor in a computer device referred to herein may alsorefer to one or more processors wherein the processor may be in onecomputing device or a plurality of computing devices acting in parallel.Additionally, any memory in a computer device referred to herein mayalso refer to one or more memories wherein the memories may be in onecomputing device or a plurality of computing devices acting in parallel.

As used herein, a processor may include any programmable systemincluding systems using micro-controllers, reduced instruction setcircuits (RISC), application specific integrated circuits (ASICs), logiccircuits, and any other circuit or processor capable of executing thefunctions described herein. The above examples are example only, and arethus not intended to limit in any way the definition and/or meaning ofthe term “processor.”

As used herein, the term “database” may refer to either a body of data,a relational database management system (RDBMS), or to both. As usedherein, a database may include any collection of data includinghierarchical databases, relational databases, flat file databases,object-relational databases, object oriented databases, and any otherstructured collection of records or data that is stored in a computersystem. The above examples are example only, and thus are not intendedto limit in any way the definition and/or meaning of the term database.Examples of RDBMS's include, but are not limited to including, Oracle®Database, MySQL, IBM® DB2, Microsoft® SQL Server, Sybase®, andPostgreSQL. However, any database may be used that enables the systemsand methods described herein. (Oracle is a registered trademark ofOracle Corporation, Redwood Shores, Calif.; IBM is a registeredtrademark of International Business Machines Corporation, Armonk, N.Y.;Microsoft is a registered trademark of Microsoft Corporation, Redmond,Wash.; and Sybase is a registered trademark of Sybase, Dublin, Calif.)

In one embodiment, a computer program is provided, and the program isembodied on a computer readable medium. In an example embodiment, thesystem is executed on a single computer system, without requiring aconnection to a sever computer. In a further embodiment, the system isbeing run in a Windows® environment (Windows is a registered trademarkof Microsoft Corporation, Redmond, Wash.). In yet another embodiment,the system is run on a mainframe environment and a UNIX® serverenvironment (UNIX is a registered trademark of X/Open Company Limitedlocated in Reading, Berkshire, United Kingdom). The application isflexible and designed to run in various different environments withoutcompromising any major functionality. In some embodiments, the systemincludes multiple components distributed among a plurality of computingdevices. One or more components may be in the form ofcomputer-executable instructions embodied in a computer-readable medium.

As used herein, an element or step recited in the singular and proceededwith the word “a” or “an” should be understood as not excluding pluralelements or steps, unless such exclusion is explicitly recited.Furthermore, references to “example embodiment” or “one embodiment” ofthe present disclosure are not intended to be interpreted as excludingthe existence of additional embodiments that also incorporate therecited features.

As used herein, the terms “software” and “firmware” are interchangeable,and include any computer program stored in memory for execution by aprocessor, including RAM memory, ROM memory, EPROM memory, EEPROMmemory, and non-volatile RAM (NVRAM) memory. The above memory types areexample only, and are thus not limiting as to the types of memory usablefor storage of a computer program.

The systems and processes are not limited to the specific embodimentsdescribed herein. In addition, components of each system and eachprocess can be practiced independent and separate from other componentsand processes described herein. Each component and process also can beused in combination with other assembly packages and processes.

The following detailed description illustrates embodiments of thedisclosure by way of example and not by way of limitation. It iscontemplated that the disclosure has general application to align databetween data storage devices during an operating system conversion.

FIG. 1 is a block diagram of an example data alignment (DA) system 100for aligning data between two data storage devices in a redundant array.In the example embodiment, system 100 includes a DA computing device102. DA computing device 102 includes a processor 104, a memory device106 in communication with processor 104, a first data storage device108, and a second data storage device 110. In some embodiments, firstand/or second data storage devices 108, 110 are separate from DAcomputing device 102. For example, first and second data storage devices108, 110 may be configured as a network attached storage (NAS) incommunication with DA computing device 102. In other embodiments, system100 may include additional, fewer, or alternative components, includingthose described elsewhere herein. For example, DA computing device 102may include three or more data storage devices.

DA computing device 102 is configured to provide one or more processesor services associated with data stored in first and second data storagedevices 108, 110. For example, DA computing device 102 may be configuredto facilitate data communication in a payment network between differentparties, such as to transmit and receiving messages regardingauthentication, authorization, settlement, and/or otherwise processingpayment transactions in the payment network. In other embodiments, DAcomputing device 102 is configured to provide a different services orprocess using the data stored in data storage devices 108, 110.

In the example embodiment, first and second data storage devices 108,110 have a data storage capacity that is divided into a plurality ofpartitions 112. Partitions 112 are subsections of data storage devices108, 110. Prior to the data alignment process described herein, firstdata storage device 108 is associated with a first operating system (OS)and second data storage device 110 is associated with a second OSdifferent from the first OS. In particular, first data storage device108 includes at least one partition 112 that is formatted according to afile system architecture associated with the first OS and similarly forsecond data storage device 110 and the second OS. In some embodiments,at least some partitions 112 are accessible by both the first and secondOSes.

Each partition 112 is associated with a block device file (not shown inFIG. 1). The block device file enables software applications (includingthe OS) to interact with partitions 112. Each block device file may beassociated with multiple partitions. Data storage devices 108, 110include one or more block device identifiers (not shown in FIG. 1) thatreference or point to the associated block device file. In someembodiments, rather than a block device file, partitions 112 may beassociated with a character device file.

To identify partitions 112 on each data storage device 108, 110, datastorage devices 108, 110 include a respective partition table 114.Partition table 114 defines information regarding each partition 112 ona respective data storage device 108 or 110, such as, but not limitedto, data storage capacity, currently used data storage, a partitionidentifier (i.e., a name of the respective partition 112), and one ormore reference pointers for arrays of partitions 112. Partition table114 is used by DA computing device to identify and interact withpartitions 112 of data storage devices 108, 110.

In the example embodiment, first data storage device 108 and/or seconddata storage device 110 include metadata 116 associated with an array ofpartitions, such as a redundant array of independent disks (RAID).Arrays are used to provide redundancy and/or performance increases ondata storage devices. For example, first data storage device 108 isconfigured in a RAID 1 configuration to include one or more mirrorsusing partitions 112 on first data storage device 108. In otherembodiments, first data storage device 108 is in a different arrayconfiguration (e.g., RAID 5 or RAID 6). In the example embodiment,metadata 116 includes a plurality of reference pointers (not shown inFIG. 1) for the partitions in the array. Each reference pointeridentifies the block device file(s) associated with a respectivepartition 112. In one embodiment, the reference pointer is the blockdevice identifier associated with partition 112. In another embodiment,the reference pointer identifies the block device identifier. In theexample embodiment, when the array is stored only on first data storagedevice 108, metadata 116 may not be stored on second data storage device110.

In the example embodiment, the array of partitions includes one or moremirrors. Each mirror includes a plurality of partitions 112. Eachpartition 112 within a mirror stores matching data. During an OSconversion from the second OS associated with second data storage device110 to the first OS associated with first data storage device 108, firstdata storage device 108 is configured to include an array of partitionsonly using partitions 112 of first data storage device 108. That is,metadata 116 of first data storage device 108 is updated to include onlyreference pointers for partitions 112 of first data storage device 108.At least one partition 112 of each mirror in the array is identified byDA computing device 102 as a “failed” device. In the example embodiment,identifying partitions 112 as failed will prevent a kernel of the firstOS from attempting to synchronize data on first data storage device 108with second data storage device 110, thereby maintaining the second OSon second data storage device 110 during testing of the first OS.

After a determination has been made to use the first OS, a dataalignment process is executed by DA computing device 102 as describedherein. The data alignment process is used to transfer the failedpartitions 112 from first data storage device 108 to second data storagedevice 110 to utilize both data storage devices without interrupting theservices or processes performed by DA computing device 102. That is, DAcomputing device 102 is not required to reboot several times toreinitialize the array of partitions with the first OS.

FIG. 2 is a block diagram of an example DA system 200 similar to system100 (shown in FIG. 1). Unlike system 100, DA system 200 includes a hostcomputing device 202 in communication with a DA computing device 220.Host computing device 202 includes one or more processors 204, a memorydevice 206, a first data storage device 208, and a second data storagedevice 210. In other embodiments, host computing device 202 includesadditional, fewer, or alternative components, including those describedelsewhere herein.

DA computing device 220 is a remote computing device that is configuredto generate a script 222 and transmit script 222 to host computingdevice 202. Script 222 is a data file storing instructions or commandsthat, when executed by processor 204, cause host computing device 202 tooperate similar to DA computing device 102 (shown in FIG. 1). Morespecifically, host computing device 222 is configured to perform a dataalignment process using first and second data storage devices 208, 210as described herein based on script 222.

In the example embodiment, DA computing device 220 is configured toretrieve one or more environment variables 224 from host computingdevice 202. Environment variables 224 include information specific tohost computing device 202, such as log file data, a device identifier,and a data storage capacity of first and second data storage devices208, 210. DA computing device 220 is further configured to populatescript 222 with environment variables 224 to enable script 222 toexecute properly on host computing device 202. That is, script 222 maybe stored as a template that is populated with environment variables 224to deploy to host computing device 202. In some embodiments, script 222is generated and executed by host computing device 202.

FIG. 3 is a data schematic of system 100 (shown in FIG. 1) during anexample data alignment process. The example data alignment process isperformed after a second OS has been stored on first data storage device108 using “failed” partitions and second data storage device 110 storesa first OS. Although first and second data storage devices 108, 110 aredepicted as separate from DA computing device 102 in FIG. 3, it is to beunderstood that DA computing device 102 may include first and/or seconddata storage devices 108, 110. In some embodiments, the data alignmentprocess may be performed under different circumstances. In otherembodiments, the data alignment process includes additional, fewer, oralternative data and/or steps, including those described elsewhereherein.

With respect to FIGS. 1 and 3, in the example embodiment, DA computingdevice 102 is configured to determine whether or not first and/or seconddata storage devices 108, 110 are undergoing synchronization or a mirrorrecovery process before aligning the data storage devices. Morespecifically, the DA computing device analyzes metadata 116 to detectany ongoing synchronization or recovery process. A synchronization orrecovery process is performed to ensure matching data is stored in eachpartition 112 of a mirror. Metadata 116 includes a state file or statedata 302 that indicates the current state of each mirror in the array.For example, but without limitation, state data 302 may identify eachmirror as “operating”, “failed”, “synchronizing”, and the like. Afterdetermining no synchronization or recovery process is occurring, DAcomputing device 102 begins the data alignment process.

DA computing device 102 is configured to set a data transfer speed forthe mirrors within the array to facilitate performing the data alignmentprocess in the background without interrupting any processes or servicesusing the data stored in first and second data storage devices 108, 110.In some embodiments, DA computing device 102 generates and transmitsinstructions to block device files 304 associated with the array mirrorsto set data transfer speed boundaries.

DA computing device 102 scans metadata 116 to identify and remove anydata associated with previous arrays. The data may include, but is notlimited to, reference pointers associated with a previously configuredarray. When DA computing device 102 detects data associated with aprevious array, DA computing device 102 overwrites or removes the datafrom metadata 116 to prevent the data from affecting the data alignmentprocess. DA computing device 102 may scan metadata 116 to remove dataassociated with any previous arrays several times throughout the dataalignment process.

DA computing device 102 updates metadata 116 stored at least by firstdata storage device 108 to remove reference pointers 306 associated withpartitions 112 identified as failed devices by the kickstartconfiguration file. As used herein, a “first subset of partitions 308”refer to partitions 112 stored by first data storage device 108 that arenot identified as failed devices, and a “second subset of partitions310” refer to partitions 112 identified as failed devices. In at leastsome embodiments, DA computing device 102 removes reference pointers 306associated with second subset of partitions 310 from metadata 116.

In the example embodiment, DA computing device 102 generates a partitiontable 312 for first and second data storage devices 108, 110. In otherembodiments, DA computing device 102 retrieves partition table 312 frommemory device 104, a remote database (not shown), and/or a differentmemory device. Partition table 312 includes data defining predeterminedpartitions 112 to be configured on the respective data storage devicethrough the data alignment process. That is, partition table 312 onfirst data storage device 108 includes data defining first subset ofpartitions 308 within first data storage device 108 and partition table312 on second data storage device 110 includes data defining secondsubset of partitions 310 within second data storage device 110. In theexample embodiment, partition table 312 for each data storage device108, 110 includes data defining both subsets of partitions 308, 310within first and second data storage devices 108, 110, respectively.Partition table 312 also includes additional information for eachpartition 112, such as data capacity, current used data size, and ablock device identifier 314 for each partition 112. Block deviceidentifier 314 is data or a pointer indicating a block device file 312associated with a partition 112. DA computing device 102 storespartition table 312 on the second data storage device 110 to overwriteprevious partitions stored by second data storage device 110, includingany previous partitions 316 associated with a previous OS (i.e., thefirst OS). For example, at least one previous partition 316 may beformatted in a file system architecture supported by the previous OS.

DA computing device 102 stores metadata 116 associated with the array ofpartitions within second data storage device 110 to facilitate movingsecond subset of partitions 310 to second data storage device 110. Inone embodiment, metadata 116 may be copied from metadata 116 stored byfirst data storage device 108. Matching copies of metadata 116 arestored on first and second data storage devices 108, 110 such that anyupdates or edits to metadata 116 are stored by both data storage devices108, 110. Matching metadata 116 enables the array of partitions tocontinue to operate even in the event of device failure.

In the example embodiment, DA computing device 102 is configured toupdate second data storage device 110 to include second subset ofpartitions 310. More specifically, DA computing device 102 removes atleast one block device identifier 314 associated with previouspartitions 316 from second data storage device 110. DA computing device102 then scans the stored partition table 312 for second subset ofpartitions 310 and generates new block device identifiers 314 for secondsubset of partitions 310 on second data storage device 110. By removingthe previous block device identifiers 314 and generating new deviceidentifiers 314 for a subset of partitions that was previouslyassociated with failed devices, DA computing device 102 has moved aportion of the array of partitions from a single data storage device totwo data storage devices without requiring the computing device to berebooted. That is, DA computing device 102 uses the hot-swap capabilityof the redundant array to move second subset of partitions 310 to seconddata storage device 110 without interrupting services or processes usingthe data stored by first and second data storage devices 108, 110.

In the example embodiment, DA computing device 102 is configured to linksecond subset of partitions 310 to the array of partitions by updatingmetadata 116 stored in first and second data storage devices 108, 110 toinclude reference pointers 306 associated with second subset ofpartitions 310. Reference pointers 306 are configured to reference oridentify the new block device identifiers 314 of second data storagedevice 110. Second subset of partitions 310 is synchronized with firstsubset of partitions 308 to mirror the data stored by first subset ofpartitions 308.

To align data storage devices 108, 110, first data storage device 108 isalso configured to match second data storage device 110 because at leastsome redundant arrays (i.e., RAID 1) require each mirror in theredundant array to include at least two matching partitions. DAcomputing device 102 performs a process for first data storage device108 similar to the process for second data storage device 110. Inparticular, in the example embodiment, DA computing device 102: (i)removes reference pointers 306 associated with first subset ofpartitions 308 from metadata 116, (ii) stores partition table 308 fromsecond data storage device 110, (iii) removes at least one block deviceidentifier 314 associated with first subset of partitions 308 from firstdata storage device 108, (iv) scans the stored partition table 308 togenerate new block device identifiers 314 for first subset of partitions308 on first data storage device 108, and (v) updates metadata 116stored in first and second data storage devices 108, 110 to includereference pointers 306 for first subset of partitions 308, therebylinking first subset of partitions 308 to the array of partitions.During configuration of first data storage device 108, second datastorage device 110 is accessible for retrieving and storing data,thereby preventing interruption of the services and/or processes usingthe stored data. After metadata 116 has been updated to includereference pointers 306 for first subset of partitions 308, the data offirst and second data storage devices 108, 110 has been aligned and thearray of partitions is configured to use both data storage devices 108,110.

In the example embodiment, DA computing device 102 expands at least onemirror of the array to include any unused space on first and second datastorage devices 108, 110. Each mirror includes at least one partition112 from each data storage device 108, 110, and therefore expanding onemirror will expand the respective partitions 112 on each data storagedevice 108, 110. DA computing device 102 then saves metadata 116 to anarray configuration file 318 associated with the redundant array suchthat the array will remain after any reboots. In some embodiments, arrayconfiguration file 318 is stored within first and/or second data storagedevices 108, 110. In other embodiments, array configuration file 318 isstored in a separate data storage device, such as an array controller(not shown). In at least some embodiments, DA computing device 102installs a boot loader 320, such as Grand Unified Bootloader (GRUB), onfirst and second data storage devices 108, 110 such that the new OS isbootable from either data storage device 108, 110. Boot loader 320 isconfigured to determine which devices, and in what order, to access toinitiate an OS.

FIG. 4 depicts an exemplary configuration of a remote or user computingdevice 402, such as DA computing device 202 (shown in FIG. 2). Computingdevice 402 may include a processor 405 for executing instructions. Insome embodiments, executable instructions may be stored in a memory area410. Processor 405 may include one or more processing units (e.g., in amulti-core configuration). Memory area 410 may be any device allowinginformation such as executable instructions and/or other data to bestored and retrieved. Memory area 410 may include one or morecomputer-readable media.

Computing device 402 may also include at least one media outputcomponent 415 for presenting information to a user 401. Media outputcomponent 415 may be any component capable of conveying information touser 401. In some embodiments, media output component 415 may include anoutput adapter, such as a video adapter and/or an audio adapter. Anoutput adapter may be operatively coupled to processor 405 andoperatively coupleable to an output device such as a display device(e.g., a liquid crystal display (LCD), organic light emitting diode(OLED) display, cathode ray tube (CRT), or “electronic ink” display) oran audio output device (e.g., a speaker or headphones). In someembodiments, media output component 415 may be configured to present aninteractive user interface (e.g., a web browser or client application)to user 401.

In some embodiments, computing device 402 may include an input device420 for receiving input from user 401. Input device 420 may include, forexample, a keyboard, a pointing device, a mouse, a stylus, a touchsensitive panel (e.g., a touch pad or a touch screen), a camera, agyroscope, an accelerometer, a position detector, and/or an audio inputdevice. A single component such as a touch screen may function as bothan output device of media output component 415 and input device 420.

Computing device 402 may also include a communication interface 425,which may be communicatively coupleable to a remote device.Communication interface 425 may include, for example, a wired orwireless network adapter or a wireless data transceiver for use with amobile phone network (e.g., Global System for Mobile communications(GSM), 3G, 4G or Bluetooth) or other mobile data network (e.g.,Worldwide Interoperability for Microwave Access (WIMAX)).

Stored in memory area 410 are, for example, computer-readableinstructions for providing a user interface to user 401 via media outputcomponent 415 and, optionally, receiving and processing input from inputdevice 420. A user interface may include, among other possibilities, aweb browser and client application. Web browsers enable users 401 todisplay and interact with media and other information typically embeddedon a web page or a website from a web server associated with a merchant.A client application allows users 401 to interact with a serverapplication associated with, for example, a vendor or business.

FIG. 5 depicts an exemplary configuration of a host computing device502, such as DA computing device 102 (shown in FIG. 1) and hostcomputing device 202 (shown in FIG. 2). Host computing device 502 mayinclude a processor 505 for executing instructions. Instructions may bestored in a memory area 510, for example. Processor 505 may include oneor more processing units (e.g., in a multi-core configuration).

Processor 505 may be operatively coupled to a communication interface515 such that host computing device 502 may be capable of communicatingwith a remote device such as computing device 402 shown in FIG. 4 oranother host computing device 502. For example, communication interface515 may receive requests from user computing device 402 via theInternet.

Processor 505 may also be operatively coupled to a storage device 525(e.g., first and second data storage devices 108, 110, shown in FIG. 1).Storage device 525 may be any computer-operated hardware suitable forstoring and/or retrieving data. In some embodiments, storage device 525may be integrated in host computing device 502. For example, hostcomputing device 502 may include one or more hard disk drives as storagedevice 525. In other embodiments, storage device 525 may be external tohost computing device 502 and may be accessed by a plurality of hostcomputing devices 502. For example, storage device 525 may includemultiple storage units such as hard disks or solid state disks in aredundant array of inexpensive disks (RAID) configuration. Storagedevice 525 may include a storage area network (SAN) and/or a networkattached storage (NAS) system.

In some embodiments, processor 505 may be operatively coupled to storagedevice 525 via a storage interface 520. Storage interface 520 may be anycomponent capable of providing processor 505 with access to storagedevice 525. Storage interface 520 may include, for example, an AdvancedTechnology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, aSmall Computer System Interface (SCSI) adapter, a RAID controller, a SANadapter, a network adapter, and/or any component providing processor 405with access to storage device 525.

Memory areas 410 (shown in FIG. 4) and 510 may include, but are notlimited to, random access memory (RAM) such as dynamic RAM (DRAM) orstatic RAM (SRAM), read-only memory (ROM), erasable programmableread-only memory (EPROM), electrically erasable programmable read-onlymemory (EEPROM), and non-volatile RAM (NVRAM). The above memory typesare example only, and are thus not limiting as to the types of memoryusable for storage of a computer program.

FIG. 6 is a flow diagram of an example method 600 for aligning data ofan array of partitions between two data storage devices using a DAsystem, such as system 100 (shown in FIG. 1). Method 600 is at leastpartially performed by a DA computing device (e.g., DA computing device102, shown in FIG. 1). In other embodiments, method 600 may includeadditional, fewer, or alternative steps, including those describedelsewhere herein.

Method 600 begins with the DA computing device updating 602 metadataassociated with an array of partitions that is stored by at least afirst data storage device to remove reference pointers for a secondsubset of partitions of the array of partitions. Removing the referencepointers also removes the second subset of partitions from the array ofpartitions. The DA computing device stores 604 a partition table withinthe first data storage device and a second data storage device. Thepartition table defines the first subset of partitions within the firstdata storage device and a second subset of partitions within the seconddata storage device. The DA computing device stores 606 the metadataassociated with the array of partitions within the second data storagedevice such that both the first and second data storage devices includea copy of the metadata. The DA computing device further updates 608 thesecond data storage device to include the second subset of partitions.In at least some embodiments, the DA computing device includes thesecond subset of partitions by removing at least one block deviceidentifier associated with previous partitions from the second datastorage device and scanning the stored partition table for the secondsubset of partitions to generate new block device identifiers for thesecond subset of partitions based on the partition table. The DAcomputing device also updates 610 the metadata stored by the first andsecond data storage devices to link the second subset of partitions backto the array of partitions. In the example embodiment, the DA computingdevice links the second subset of partitions to the array of partitionsby updating 610 the metadata to include the reference pointers of thesecond subset of partitions. The reference pointers for the secondsubset of partitions are associated with the new block deviceidentifiers for the second subset of partitions.

In the example embodiment, in response to linking the second subset ofpartitions to the array of partitions, the DA computing device aligns612 the first subset of partitions with the second subset of partitions.In some embodiments, the DA computing device aligns 612 the two subsetsof partitions by (i) removing the reference pointers associated with thefirst subset of partitions from the metadata, (ii) removing at least oneblock device identifier associated with the array of partitions from thefirst data storage device, (iii) scanning the stored partition table forthe first subset of partitions to generate new block device identifiersfor the first subset of partitions on the first data storage device, and(iv) updating the metadata to include the reference pointers for thefirst subset of partitions.

FIG. 7 is a diagram 700 of components of one or more example computingdevices that may be used in the method shown in FIG. 6. FIG. 7 furthershows a configuration of a data storage system 710 coupled to severalseparate components within DA computing device 102 (shown in FIG. 1),which perform specific tasks.

DA computing device 102 includes an updating component 702 configured toupdate metadata associated with an array of partitions to removereference pointers for a second subset of partitions. Updating component702 is further configured to update the second data storage device toinclude the second subset of partitions by removing at least one blockdevice identifier associated with previous partitions from the seconddata storage device and scanning a stored partition table for the secondsubset of partitions to generate new block device identifiers for thesecond subset of partitions. DA computing device 102 also includes astoring component 704 configured to store a partition table thatidentifies the first and second subset of partitions at the first andsecond data storage devices. Storing component 704 is further configuredto store the metadata associated with the array of partitions within thesecond data storage device. DA computing device 102 further includes alinking component 706 configured to link the second subset of partitionsto the array of partitions by updating the metadata to include thereference pointers of the second subset of partitions that areassociated with the new block device identifiers. In at least someembodiments, DA computing device 102 further includes an aligningcomponent 708 configured to align the first and second subset ofpartitions by (i) removing reference pointers associated with the firstsubset of partitions from the metadata, (ii) removing at least one blockdevice identifier associated with the array of partitions from the firstdata storage device, (iii) scanning the stored partition table for thefirst subset of partitions to generate new block device identifiers forthe first subset of partitions on the first data storage device, and(iv) updating the metadata to include the reference pointers for thefirst subset of partitions.

In an exemplary embodiment data storage system 710 is divided into aplurality of sections, including but not limited to, an array datasection 712, an OS data section 714, a device metadata section 716, anda script data section 718. These sections are interconnected through DAcomputing device 102 to update and retrieve the information as required.

As will be appreciated based on the foregoing specification, theabove-discussed embodiments of the disclosure may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware or any combination or subset thereof. Anysuch resulting computer program, having computer-readable and/orcomputer-executable instructions, may be embodied or provided within oneor more computer-readable media, thereby making a computer programproduct, i.e., an article of manufacture, according to the discussedembodiments of the disclosure. These computer programs (also known asprograms, software, software applications or code) include machineinstructions for a programmable processor, and can be implemented in ahigh-level procedural and/or object-oriented programming language,and/or in assembly/machine language. As used herein, the terms“machine-readable medium,” “computer-readable medium,” and“computer-readable media” refer to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The “machine-readable medium,” “computer-readable medium,” and“computer-readable media,” however, do not include transitory signals(i.e., they are “non-transitory”). The term “machine-readable signal”refers to any signal used to provide machine instructions and/or data toa programmable processor.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal languages of the claims.

1-24. (canceled)
 25. A data alignment (DA) computing device configuredto facilitate transition to a new operating system (“OS”) on a redundantarray storage system, the DA computing device comprising: a processorcommunicatively coupled to a first data storage device and a second datastorage device each operating under an initial OS, the first datastorage device comprising a first subset of partitions and the seconddata storage device comprising a second subset of partitions, the firstand second subsets of partitions forming a mirrored array of partitionsdefined by metadata stored on the first and second storage devices; anda memory in communication with the processor, the memory storinginstructions that, when executed by the processor, cause the processorto: execute a configuration file that identifies the second subset ofpartitions as a failed device; alter metadata to remove the secondsubset of partitions from the mirrored array of partitions; install thenew OS on the first data storage device, wherein the first data storagedevice operates under the new OS at least partially concurrently withthe second subset of partitions being identified as the failed device;after verifying an operability of the new OS on the first storagedevice, (i) update the metadata to re-establish the second subset ofpartitions as part of the mirrored array of partitions on the seconddata storage device and (ii) install the new OS on the second datastorage device.
 26. The DA computing device in accordance with claim 25,wherein the metadata includes reference pointers to each partition ofthe first and second subsets of partitions.
 27. The DA computing devicein accordance with claim 25, wherein the initial OS remains stored onthe second storage device while the second subset of partitions isidentified as the failed device.
 28. The DA computing device inaccordance with claim 25, wherein the instructions, when executed by theprocessor, further cause the processor to update the metadata tore-establish the second subset of partitions by: removing at least oneblock device identifier associated with previous partitions from thesecond data storage device, wherein the previous partitions were definedprior to updating the metadata to remove the reference pointers; andgenerating new block device identifiers to be associated with there-established second subset of partitions within the second datastorage device.
 29. The DA computing device in accordance with claim 28,wherein the previous partitions of the second data storage deviceinclude at least one partition associated with the initial OS, whereinthe at least one partition is removed from the second data storagedevice when removing the at least one block device identifier associatedwith the previous partitions from the second data storage device. 30.The DA computing device in accordance with claim 25, wherein theinstructions, when executed by the processor, further cause theprocessor to update the metadata to re-establish the first subset ofpartitions by: removing at least one block device identifier associatedwith previous partitions of the first data storage device, wherein theprevious partitions were defined prior to installing the new OS; andgenerating new block device identifiers to be associated with there-established first subset of partitions within the first data storagedevice.
 31. The DA computing device in accordance with claim 30, whereinthe instructions, when executed by the processor, further cause theprocessor to configure the re-established first subset of partitionswithin the first data storage device and the re-established secondsubset of partitions within the second data storage device in aredundant array of independent disks (RAID) 1 configuration.
 32. Amethod for facilitating transition to a new operating system (“OS”) on aredundant array storage system including a first data storage device anda second data storage device each operating under an initial OS, thefirst data storage device comprising a first subset of partitions andthe second data storage device comprising a second subset of partitions,the first and second subsets of partitions forming a mirrored array ofpartitions defined by metadata stored on the first and second storagedevices, said method comprising: executing, by a data alignment (DA)computing device, a configuration file that identifies the second subsetof partitions as a failed device; altering, by the DA computing device,metadata to remove the second subset of partitions from the mirroredarray of partitions; installing, by the DA computing device, the new OSon the first data storage device, wherein the first data storage deviceoperates under the new OS at least partially concurrently with thesecond subset of partitions being identified as the failed device; afterverifying an operability of the new OS on the first storage device, (i)updating, by the DA computing device, the metadata to re-establish thesecond subset of partitions as part of the mirrored array of partitionson the second data storage device and (ii) installing, by the DAcomputing device, the new OS on the second data storage device.
 33. Themethod in accordance with claim 32, wherein the metadata includesreference pointers to each partition of the first and second subsets ofpartitions.
 34. The method in accordance with claim 32, wherein theinitial OS remains stored on the second storage device while the secondsubset of partitions is identified as the failed device.
 35. The methodin accordance with claim 32, wherein updating the metadata tore-establish the second subset of partitions comprises: removing atleast one block device identifier associated with previous partitionsfrom the second data storage device, wherein the previous partitionswere defined prior to updating the metadata to remove the referencepointers; and generating new block device identifiers to be associatedwith the re-established second subset of partitions within the seconddata storage device.
 36. The method in accordance with claim 35, whereinthe previous partitions of the second data storage device include atleast one partition associated with the initial OS, and wherein removingthe at least one block device identifier associated with the previouspartitions from the second data storage device comprises removing the atleast one partition from the second data storage device.
 37. The methodin accordance with claim 32, further comprising updating the metadata tore-establish the first subset of partitions by: removing at least oneblock device identifier associated with previous partitions of the firstdata storage device, wherein the previous partitions were defined priorto installing the new OS; and generating new block device identifiers tobe associated with the re-established first subset of partitions withinthe first data storage device.
 38. The method in accordance with claim37, further comprising configuring the re-established first subset ofpartitions within the first data storage device and the re-establishedsecond subset of partitions within the second data storage device in aredundant array of independent disks (RAID) 1 configuration.
 39. Atleast one non-transitory computer-readable storage media havingcomputer-executable instructions embodied thereon for facilitatingtransition to a new operating system (“OS”) on a redundant array storagesystem including a first data storage device and a second data storagedevice each operating under an initial OS, the first data storage devicecomprising a first subset of partitions and the second data storagedevice comprising a second subset of partitions, the first and secondsubsets of partitions forming a mirrored array of partitions defined bymetadata stored on the first and second storage devices, wherein whenexecuted by at least one processor, the computer-executable instructionscause the at least one processor to: execute a configuration file thatidentifies the second subset of partitions as a failed device; altermetadata to remove the second subset of partitions from the mirroredarray of partitions; install the new OS on the first data storagedevice, wherein the first data storage device operates under the new OSat least partially concurrently with the second subset of partitionsbeing identified as the failed device; after verifying an operability ofthe new OS on the first storage device, (i) update the metadata tore-establish the second subset of partitions as part of the mirroredarray of partitions on the second data storage device and (ii) installthe new OS on the second data storage device.
 40. The computer-readablestorage media in accordance with claim 39, wherein the metadata includesreference pointers to each partition of the first and second subsets ofpartitions.
 41. The computer-readable storage media in accordance withclaim 39, wherein the initial OS remains stored on the second storagedevice while the second subset of partitions is identified as the faileddevice.
 42. The computer-readable storage media in accordance with claim39, wherein the computer-executable instructions further cause theprocessor to update the metadata to re-establish the second subset ofpartitions by: removing at least one block device identifier associatedwith previous partitions from the second data storage device, whereinthe previous partitions were defined prior to updating the metadata toremove the reference pointers; and generating new block deviceidentifiers to be associated with the re-established second subset ofpartitions within the second data storage devices.
 43. Thecomputer-readable storage media in accordance with claim 42, wherein theprevious partitions of the second data storage device include at leastone partition associated with the initial OS, wherein the at least onepartition is removed from the second data storage device when removingthe at least one block device identifier associated with the previouspartitions from the second data storage device.
 44. Thecomputer-readable storage media in accordance with claim 39, wherein thecomputer-executable instructions further cause the processor to updatethe metadata to re-establish the first subset of partitions by: removingat least one block device identifier associated with previous partitionsof the first data storage device, wherein the previous partitions weredefined prior to installing the new OS; and generating new block deviceidentifiers to be associated with the re-established first subset ofpartitions within the first data storage device.